This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
don't bother ~Lex Prelutexflar 11.Aug.03 10:50 AM a Web browser Domino Server 6.0.1Windows 2000
The suggested "fix" is to start the machine in safe boot mode. In fact, just renaming js32.dll and nxmlcommon.dll allowed the upgrade to work for my server.
Here's the suggested Lotus workaround, to save you the trouble of looking it up:
======================================
In this case the workaround was to invoke the Safe Mode during booting the operating system. This process of booting loads a minimal set of device drivers and services invoked by pressing F8 when prompted during booting to enter Safe Mode. Once Safe Mode is invoked, a Windows Advanced Options menu will display a listing of different Safe Mode options available.
The option you select depends on where the Domino install media is located. If a CD-ROM is being used, choose Safe Mode. If installing from a network share, choose Safe Mode with Networking. Behind the scenes, Windows 2000 dynamically adds switches to the boot.ini arc path such as "/safeboot: minimal" for basic Safe Mode or "/safeboot: network" for the networked Safe Mode option.
This also works if there is an error with the js32.dll file. The benefit of upgrading Domino with this method is that js32.dll is no longer a locked file, and the installation will run to completion as designed. Once the upgrade is finished, reboot the server and allow the Windows 2000 operating system to start normally. The Domino server then starts up without error.
Alternatively, renaming js32.dll to oldjs32.dll seems to allow the upgrade to finish as well.
Return to top
. . . . . . . . don't bother (~Lex Prelutexfl... 11.Aug.03)
Print this page
